Skip to main content
Feedback

Integration runtimes

To run your integration processes and APIs, they are deployed to an integration runtime. An integration runtime is a self-contained engine that securely connects directly to your endpoint applications and data sources and performs the integration process logic.

There are several options when selecting a runtime, starting first with whether to use a Boomi-hosted runtime cloud or a local runtime. Boomi-hosted runtimes are completely managed and maintained by Boomi. Local runtimes are customer-hosted and are installed, managed, and maintained by your team.

Boomi-hosted runtime clouds

Boomi offers several hosted runtime cloud options to fit different processing volumes, infrastructure needs, and budgets. All cloud options are available in regions around the world. They are fully managed, operated, and monitored by Boomi so you can focus on building integrations and APIs.

These include:

  • Public Cloud service (PCS) A multi-tenant cloud service with various tiers to choose from.
  • Dedicated Cloud service (DCS) A single-tenant cloud service, offering a higher performance, additional authorization option, and VPN capabilities.
  • Managed Cloud service (MCS) A single-tenant cloud service with custom scaling/sizing and dedicated monitoring and advisory services.

All accounts include at least one attachment to a Public Cloud (base tier). For information and pricing on the additional hosted runtime options, contact your Boomi account representative.

Customer-hosted runtimes

Customer-hosted runtimes are installed and managed by your team in an infrastructure of your choice. You can install local runtimes in a public cloud providers such as Amazon, Azure, or Google, or on-premises on a server within your network.

There are three types of runtimes:

  • Basic runtime - Lightweight, dynamic runtime engine containing all the components required to run your processes from end to end, including connectors, transformation rules, decision handling, and processing logic.
  • Cluster - A single-tenant, clustered runtime that allows for multiple runtime processes to run concurrently.
  • Runtime cloud - Consists of one or more runtime cloud clusters installed on multiple machines. The runtime cloud clusters on the machines are grouped together to form the runtime cloud.

Cloud Considerations

If you use the cloud model, you can deploy your integration processes to a runtime cloud.

If you use a local model, Boomi provides the basic runtime, a lightweight Java application deployed on a host with internet access.

If you use the local model and any of the following applies, consider utilizing a runtime cluster:

  • Providing a high availability, load-balanced solution
  • Change the basic runtime's process time or handling
  • Concerned that the basic runtime's process might not run because of an outage

If you need a multi-tenant solution to accommodate multiple customer accounts, consider setting up your own local runtime cloud.

Runtime options comparison

The following table compares the features of the runtime options:

FeaturesBasic runtimeRuntime clusterPrivate runtime cloudBoomi runtime cloud
Multi-tenancy, which multiple accounts can useNot Supported not supportedNot Supported not supportedSupported supportedSupported supported
Disk space monitoringNot Supported not supportedNot Supported not supportedSupported supportedSupported supported
Forked execution (disabled by default on runtime clusters)Not Supported not supportedSupported supportedSupported supportedSupported supported
Multiple nodes providing load balancing and failover supportNot Supported not supportedSupported supportedSupported supportedSupported supported
Supports integrations that generate and receive high volumeNot Supported not supportedSupported supportedSupported supportedSupported supported
Available to customersSupported supportedSupported supportedSupported supportedSupported supported
Available to Boomi partnersSupported supportedSupported supportedSupported supportedSupported supported

Runtime terminology

If you work with basic runtimes, runtime clusters, and runtime clouds, become familiar with the following terminology:

  • Process – An integration process.
  • Execution – An instance of a process running on a basic runtime. It is single-threaded.
  • JVM – A single operating system process, running on the Java platform.
  • Cluster – One or more JVMs working together as a logical runtime cluster or Cloud.
  • Node – A single runtime cluster or Cloud JVM running as part of a cluster.
  • Basic runtime – A single-tenant, single-node runtime engine.
  • Runtime cluster – A single-tenant, multiple-node runtime engine.
  • Cloud – A multiple-tenant, multiple-node runtime engine.
  • Forked Execution – A separate, special-purpose JVM running a single process.
  • Computer – A single computer, which can be a physical or virtual machine.
  • CPU – A processor in a computer, including physical, not virtual, cores.
  • Memory or RAM – The transient working memory available for the CPU.
  • Hard Disk or Storage – The persistent, long-term data storage available on the computer.
  • Heap – The transient working memory for a JVM. A subset of memory is owned and managed by a Java process.
  • Garbage Collection – The algorithm used by Java to manage the Heap usage, constantly running in the background.
  • Thread – An running code path within a JVM.
On this Page